Techniques for messaging bot controls based on machine-learning user intent detection

ABSTRACT

Techniques for messaging bot controls based on machine-learning user intent detection are described. In one embodiment, an apparatus may comprise a message queue monitoring component operative to monitor a messaging interaction, the messaging interaction exchanged via a messaging system, the messaging interaction involving at least one client device; an interaction processing component operative to determine a user intent for the messaging interaction; and a bot management component operative to determine a messaging bot options configuration for the client device based on the user intent; and send the messaging bot options configuration to the client device. Other embodiments are described and claimed.

RELATED APPLICATIONS

This application claims the benefit of priority under 35 U.S.C. §119(e)to U.S. Provisional Patent Application No. 62/320,869, titled“Techniques to Respond to User Requests Using Natural-Language MachineLearning Based on Example Conversations,” attorney docket number1360F0136Z, filed on Apr. 11, 2016, which is hereby incorporated byreference in its entirety.

This application claims the benefit of priority under 35 U.S.C. §119(e)to U.S. Provisional Patent Application No. 62/321,082, titled“Techniques for Messaging Agent Interactions,” attorney docket number1360F0137Z, filed on Apr. 11, 2016, which is hereby incorporated byreference in its entirety.

This application is related to U.S. patent application Ser. No.15/350,004, titled “Techniques for Device Configuration for CommerceMessaging Using Commerce Messaging History Information,” attorney docketnumber 1360F0139.1, filed on Nov. 11, 2016, which is hereby incorporatedby reference in its entirety.

BACKGROUND

Users may interact with each other in a messaging system, sendingmessages back and forth to each other in a text-based conversationbetween two or more users. A user may have a user account associatedwith them in the messaging system, the user account providing an onlineidentity for the user, a destination for messages directed to the user,and generally coordinating the user's access to and use of the messagingsystem. A user may access the messaging system from a variety ofendpoints, including mobile devices (e.g., cellphones), desktopcomputers, web browsers, specialized messaging clients, etc.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some novel embodiments described herein. This summaryis not an extensive overview, and it is not intended to identifykey/critical elements or to delineate the scope thereof. Some conceptsare presented in a simplified form as a prelude to the more detaileddescription that is presented later.

Various embodiments are generally directed to techniques for messagingbot controls based on machine-learning user intent detection. Someembodiments are particularly directed to techniques for messaging botcontrols based on machine-learning user intent detection, in which amessaging interaction is augmented with messaging bot options. In oneembodiment, for example, an apparatus may comprise a message queuemonitoring component operative to monitor a messaging interaction, themessaging interaction exchanged via a messaging system, the messaginginteraction involving at least one client device; an interactionprocessing component operative to determine a user intent for themessaging interaction; and a bot management component operative todetermine a messaging bot options configuration for the client devicebased on the user intent; and send the messaging bot optionsconfiguration to the client device. Other embodiments are described andclaimed.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative of the various ways in which the principles disclosed hereincan be practiced and all aspects and equivalents thereof are intended tobe within the scope of the claimed subject matter. Other advantages andnovel features will become apparent from the following detaileddescription when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a consumer-to-business messagingsystem.

FIG. 2 illustrates an embodiment of a social graph.

FIG. 3A illustrates a user interface with a message interaction displaywith messaging bot invocation controls.

FIG. 3B illustrates a user interface with a messaging bot menu.

FIG. 3C illustrate a user interface for an updated messaging bot menuwith updated customization options.

FIG. 3D illustrate a user interface for a messaging bot menu for adifferent messaging bot with customization options carried over betweenmessaging bots.

FIG. 4A illustrates a user interface for a messaging bot menu for aconfigured service request.

FIG. 4B illustrates a user interface for a message interaction displaywith persistent messaging bot invocation controls.

FIG. 4C illustrates a user interface with a restored messaging bot menu.

FIG. 4D illustrates a user interface with a message interaction displaywith administrative text communication a service request.

FIG. 5 illustrates a determination of a user intent based on a messaginginteraction.

FIG. 6 illustrates a messaging bot options configuration based on a userintent.

FIG. 7 illustrates an embodiment of a logic flow for the system of FIG.1.

FIG. 8 illustrates an embodiment of a centralized system for the systemof FIG. 1.

FIG. 9 illustrates an embodiment of a distributed system for the systemof FIG. 1.

FIG. 10 illustrates an embodiment of a computing architecture.

FIG. 11 illustrates an embodiment of a communications architecture.

FIG. 12 illustrates an embodiment of a radio device architecture.

DETAILED DESCRIPTION

Network-connected computing devices can provide their users with anunprecedented ability to engage in interpersonal communication. Peoplemay engage in messaging interactions with their friends, family,coworkers, and other associates. A user's message exchanges with theircontacts may each be maintained within a distinct message thread.

These network-connected computing devices can also provide their userswith access to network-accessible services. For instance, transportationservices, dining services, entertainment services, and other servicesmay use web sites, web applications, client applications, or othernetwork-accessibility techniques to empower people to use their clientdevices to engage with their services. In some cases, such as someentertainment or media services, the service can be both arranged anddelivered via the client devices. For example, music may be purchasedvia a client device and delivered to the client device for playback. Inother cases, such as with transportation, dining, and in-personentertainment, the service can be arranged via the client devices, butis performed external to the client device. For example, a ride-sharingservice may be arranged via a client device but performed through avehicle and driver providing ride sharing to the user.

In some cases, the use of a network-accessible service may relate tomore than one person. Particularly where a user's access to the serviceis a client device that they also use for messaging, a user may benefitfrom sharing their engagement with the network-accessible service in themessaging client with the others to whom the service relates. As such,message threads may act as hubs for a user's online social relationshipwith their contacts, with the message threads incorporating servicesrequested, monitored, or engaged with via the same client used formessaging.

To aid a user in interacting with a service via a messaging context,services may be represented as messaging bots within a messaging system.A messaging bot may be an automated front-end to a network-accessibleservice that can be represented as a participant within a messagethread. In some cases, a messaging bot may be corresponded with in amessage thread that explicitly includes the messaging bot, such as aone-on-one message thread between a particular user and the messagingbot. In other cases, a messaging bot may be corresponded with in amessage thread in which the messaging bot is not a regular participant,the messaging bot a temporary participant in the message thread for thepurposes of interacting with the service. The messaging bot may beincluded as a temporary participant in any other thread, whether aone-on-one thread between two users or a group thread between multipleusers.

In some cases, the use of a network-accessible service may relate tomore than one person. Particularly where a user's access to the serviceis a client device that they also use for messaging, a user may benefitfrom sharing their engagement with the network-accessible service in themessaging client with the others to whom the service relates. As such,message threads may act as hubs for a user's online social relationshipwith their contacts, with the message threads incorporating servicesrequested, monitored, or engaged with via the same client used formessaging.

To aid a user in interacting with a service via a messaging context,services may be represented as messaging bots within a messaging system.A messaging bot may be an automated front-end to a network-accessibleservice that can be represented as a participant within a messagethread. In some cases, a messaging bot may be corresponded with in amessage thread that explicitly includes the messaging bot, such as aone-on-one message thread between a particular user and the messagingbot. In other cases, a messaging bot may be corresponded with in amessage thread in which the messaging bot is not a regular participant,the messaging bot a temporary participant in the message thread for thepurposes of interacting with the service. The messaging bot may beincluded as a temporary participant in any other thread, whether aone-on-one thread between two users or a group thread between multipleusers.

As such, a user may engage with network services within the familiarexperience of a messaging client. Further, by using a messaging client,a user may engage with network services within a messaging context so asto allow the inclusion of other people. In some cases, this may simplyinform the other people as to the services, such as letting friends orfamily know about transportation details. In other cases, this mayempower the performance of services for multiple people, such as wheredinner, a ride, entertainment, or other service is arranged for the useof multiple people. As a result, the embodiments can improve theexperience of using network-accessible services and can extend the reachof network-accessible services to the user of a messaging system.

Therefore, users may engage with a business via a page in a socialnetworking service using messaging communication, as they may befamiliar with from chatting with friends. Users may discover, engagewith, and purchase products and services from these businesses in thesame messaging application they use for communicating with friends,colleagues, and other acquaintances.

Initially, users may be accustomed to interacting with a business via aweb page. Even where this web page contains interactive or dynamicelements, the interaction is still received in the presentation style ofa web page. Business pages, similar to web pages, may be accessible viaa messaging system. However, where a web page may empower chatting via apop-up dialog box, a messaging system may display a conversationalinteraction with a business in a messaging-specific interface. This mayserve to ground the interaction in the presentation style of messaging,thereby humanizing and personalizing the experience. Further, as withmessaging with another person, the messaging client may maintain ahistory of a conversation, allow navigation away from the conversationand returning, and a mirroring of the conversation across multiple userdevices. In contrast, a pop-up messaging dialog on a web page istemporary, stuck to a browser window that cannot be closed until theconversation is completed, and rooted in a single user device. Thisconversation with a business page may be represented by a messaging bot,the messaging bot a virtual representation of the business page in amessaging environment. The messaging bot may function as an avatar forthe business and unify the experience of messaging with a businesswithin a single messaging representation.

Users may be suggested businesses with which to engage with. Thesesuggestions may be made within the context of a message thread betweentwo or more users. As such, these suggestions may be made usingtechniques that control the amount of screen space used to display thesuggestions. These suggestions may be controls that, when selected,instantiate a larger interface for the configuration of a servicerequest with a messaging bot. This larger interface may be customizedbased on the context of a user's conversation and the information knownabout one or more users. This customization may include thepre-selection of various user-customizable options and/or may includeselecting a portion of a menu for a messaging bot. As a result, theembodiments can reduce the friction and clutter of integrating messagingbots into a message thread.

Reference is now made to the drawings, wherein like reference numeralsare used to refer to like elements throughout. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding thereof. It maybe evident, however, that the novel embodiments can be practiced withoutthese specific details. In other instances, well known structures anddevices are shown in block diagram form in order to facilitate adescription thereof. The intention is to cover all modifications,equivalents, and alternatives consistent with the claimed subjectmatter.

It is worthy to note that “a” and “b” and “c” and similar designators asused herein are intended to be variables representing any positiveinteger. Thus, for example, if an implementation sets a value for a=5,then a complete set of components 122 illustrated as components 122-1through 122-a may include components 122-1, 122-2, 122-3, 122-4 and122-5. The embodiments are not limited in this context.

FIG. 1 illustrates a block diagram for a consumer-to-business messagingsystem 100. In one embodiment, the consumer-to-business messaging system100 may comprise a computer-implemented system having softwareapplications comprising one or more components. Although theconsumer-to-business messaging system 100 shown in FIG. 1 has a limitednumber of elements in a certain topology, it may be appreciated that theconsumer-to-business messaging system 100 may include more or lesselements in alternate topologies as desired for a given implementation.

A consumer-to-business service 110 may serve as an intermediary betweenconsumers and businesses. Consumers and businesses may both be users ofthe consumer-to-business service 110, with consumers represented via anindividual user account and businesses represented by a commerce accountand, possibly, one or more individual user accounts associated with thebusiness, such as individual user accounts associated withrepresentatives and other employees of the business. A consumer user maybe represented with a user entity in a social graph. A business or othercommercial user may be represented by a business entity in a socialgraph. The relationship between the consumer user and the commercialuser may be represented by one or more edges between the user entity andbusiness entity in the social graph.

The consumer-to-business service 110 may comprise a messaging system140. The messaging system 140 may be generally arranged to receive,store, and deliver messages between individual entities such asindividual users and collective entities such as businesses and otherorganizations. The messaging system 140 may store messages whilemessaging endpoints, such as messaging endpoint 125, are offline anddeliver the messages once the messaging endpoints are available. Themessaging system 140 may empower a user to use multiple messagingendpoints (e.g., a messaging client on a mobile device, a web browser ona personal computer) for the same user account, with the messagingsystem 140 keeping all of the messaging endpoints up-to-date as to themessaging state of the user account.

The consumer-to-business service 110 may comprise a social networkingservice 130. The social networking service 130 may maintain a socialgraph data structure representing a social graph. The social graph mayrepresent relationships between entities, such as user entities,commerce entities, and any other sort of entity. The social graph mayrepresent the relationships as graph relationships, in which allinformation is encoded as either being attached to a particular node inthe graph or attached to a particular edge between two nodes in thegraph. A messaging system 140 may be an element of a social networkingservice 130, with the social graph containing, at least in part,social-networking information. The whole of the consumer-to-businessservice 110 may be an element or composed of elements of a socialnetworking service.

The consumer-to-business service 110 may comprise a consumer portal 150.The consumer portal 150 may be a unified entry point into theconsumer-to-business service 110 for client applications being used byconsumers. The consumer portal 150 may serve as a general user portalfor non-commerce entities, including users that are not or do not engagein commerce using the consumer-to-business service 110. The consumerportal 150 may provide access to the messaging system 140 and the socialnetworking service 130. In some embodiments, all access to the socialnetworking service 130 may be mediated by the consumer portal 150 inwhich the information of the social networking service 130 is used andmanaged on behalf of the user without the user having direct access tosome or all of the social graph information. In some embodiments, theuser may have direct access to the messaging system 140 using their useraccount, with the consumer portal 150 limited to consumer functions ofthe consumer-to-business service 110 with general messagingfunctionality (e.g., messaging with friends) provided through directnetwork communication between the messaging endpoint 125 and themessaging system 140 without the mediation of the consumer portal 150.

The consumer-to-business service 110 may comprise a business portal 160.The business portal 160 may be a unified entry point into theconsumer-to-business service 110 for client application being used bybusiness entities. The business portal 160 may provide access to themessaging system 140 and the social networking service 130. In someembodiments, all access to the social networking service 130 may bemediated by a business portal 160 in which the information of the socialnetworking service 130 is used and managed on behalf of the businessentity without the business entity having direct access to some or allof the social graph information. In some embodiments, the businessentity may have direct access to the messaging system 140 using theircommerce account, with the business portal 160 limited to businessfunctions of the consumer-to-business service 110 with general messagingfunctionality (e.g., messaging with customers) provided through directnetwork communication between one or more messaging bots 190 and themessaging system 140 without the mediation of the business portal 160.

A user may participate in the consumer-to-business messaging system 100and interact with the consumer-to-business service 110 using a messagingendpoint 125 software application executing on a client device 120. Theclient device 120 may typically be a smartphone—a mobile phone capableof executing software applications that provide functionality beyondthat of a conventional telephone—such as an iPhone®, Android® phone, orother smartphone. The messaging endpoint 125 may be specificallyassociated with a particular messaging system 140 that forms part of theconsumer-to-business service 110 or may be a general-purpose messagingclient operative to interact with a plurality of messaging services. Themessaging endpoint 125 may interact with one or both of the consumerportal 150 and the messaging system 140 for the performance of messagingtasks and commerce tasks.

A business entity may be represented in a messaging system by a commercerepresentation comprising a collection of information for display to auser. A commerce representation may comprise a business page, thebusiness page being the identity of a business within theconsumer-to-business messaging system 100. The business page may displayinformation regarding a business entity. The business page may includeinformation for the business entity, such as one or more of a physicallocation for the business entity, the operating hours of the physicallocation, or the hours in which the business entity (e.g., arepresentative of the business entity) is available for messagingthrough the consumer-to-business messaging system 100. The business pagemay include social-networking information for the business entity, suchas a list of friends of a viewing user that have “liked” or “followed”the business entity within a social network as may be represented in asocial graph.

A commerce representation may not correspond precisely to a businessentity. A single business entity, such as a business, may have multiplecommerce representations and therefore multiple business pages. Forexample, a single business may have different representations fordifferent brands owned and operated by the same business. A retailer orreseller may sell multiple brands and may have different representationsfor different brands that they sell. A business may have differentrepresentations for different geographic areas in which they operate,such as one business page for the United States, another for Europe,another for Russia, etc.

To aid a user in interacting with a service within a messaging context,services may be represented as messaging bots 190 within a messagingsystem. A messaging bot may be a fully or partially automated front-endto a network-accessible service that can be represented as a participantwithin a message thread. In some cases, a messaging bot may becorresponded with in a message thread that explicitly includes themessaging bot, such as a one-on-one message thread between a particularuser and the messaging bot. In other cases, a messaging bot may becorresponded with in a message thread in which the messaging bot is nota regular participant, the messaging bot a temporary participant in themessage thread for the purposes of interacting with the service. Themessaging bot may be included as a temporary participant in any otherthread, whether a one-on-one thread between two users or a group threadbetween more than two users.

A messaging bot for a commerce representation may be presented in amessaging conversation in a messaging system 140. A user of themessaging system 140 may interact with a business by messaging with themessaging bot that comprises a virtual representation of the business. Amessaging bot may specifically correspond to a commerce representationpresented as a business page, with the messaging bot being therepresentation of the business page in a messaging context. Messagingwith the bot may therefore extend the presence of a commercerepresentation from a business page, primarily dedicated to providinginformation from the business to users, to interactive messaging inwhich users and the business can engage in a conversation.

A business may use one or more commerce applications to engage with themessaging system 140. An application may correspond to a specificregistration empowering access to the messaging system 140 and/or socialnetworking service 130 via an application programming interface (API).An application may be registered with the messaging system 140 viavarious registered hooks for the application specifying how theapplication can be contacted by the messaging system 140. These hooksmay be used to contact the application in response to events, such asuser messaging, within the messaging system 140. An application may beassigned a secure token that may be used for authentication and thesecure (e.g., encrypted) reception and sending of information with themessaging system 140. An application may correspond to a specific AppIDwith the messaging system 140 and/or social networking service 130.Because the business may surface multiple aspects of the services andproducts it provides via the agent, multiple different applications maybe used by a business entity to interact with a user via the messagingsystem 140. Each application may be subscribed with the messaging system140 to the one or more commerce representations, such as business pages,that it powers.

The network 180 may comprise any form of computer network operative tocarry computer transmissions between computer devices. The network 180may include one or both of intranets and the Internet. The network 180may include cellular data and/or Wi-Fi data networks, such as may beused to provide connectivity to a mobile client device 120.

The consumer-to-business messaging system 100 may use knowledgegenerated from interactions between users. The consumer-to-businessmessaging system 100 may comprise a component of a social networkingservice 130 and may use knowledge generated from the broaderinteractions of the social networking service 130. As such, to protectthe privacy of the users of the consumer-to-business messaging system100 and the larger social networking service 130, consumer-to-businessmessaging system 100 may include an authorization server (or othersuitable component(s)) that allows users to opt in to or opt out ofhaving their actions logged by the consumer-to-business messaging system100 or shared with other systems (e.g., third-party systems), forexample, by setting appropriate privacy settings. A privacy setting of auser may determine what information associated with the user may belogged, how information associated with the user may be logged, wheninformation associated with the user may be logged, who may loginformation associated with the user, whom information associated withthe user may be shared with, and for what purposes informationassociated with the user may be logged or shared. Authorization serversor other authorization components may be used to enforce one or moreprivacy settings of the users of the consumer-to-business messagingsystem 100 and other elements of a social networking service 130 throughblocking, data hashing, anonymization, or other suitable techniques asappropriate. For example, while interactions between users of a socialnetworking service 130 and the social networking service 130 may be usedto learn media content preferences and the relationship betweenpreferences for different pieces of content, these interactions may beanonymized prior to or as part of the learning process.

FIG. 2 illustrates an example of a social graph 200. In particularembodiments, a social-networking system may store one or more socialgraphs 200 in one or more data stores as a social graph data structure.

In particular embodiments, social graph 200 may include multiple nodes,which may include multiple user nodes 202 and multiple concept nodes204. Social graph 200 may include multiple edges 206 connecting thenodes. In particular embodiments, a social-networking system, clientsystem, third-party system, or any other system or device may accesssocial graph 200 and related social-graph information for suitableapplications. The nodes and edges of social graph 200 may be stored asdata objects, for example, in a data store (such as a social-graphdatabase). Such a data store may include one or more searchable orqueryable indexes of nodes or edges of social graph 200.

In particular embodiments, a user node 202 may correspond to a user ofthe social-networking system. As an example and not by way oflimitation, a user may be an individual (human user), an entity (e.g.,an enterprise, business, or third-party application), or a group (e.g.,of individuals or entities) that interacts or communicates with or overthe social-networking system. In particular embodiments, when a userregisters for an account with the social-networking system, thesocial-networking system may create a user node 202 corresponding to theuser, and store the user node 202 in one or more data stores. Users anduser nodes 202 described herein may, where appropriate, refer toregistered users and user nodes 202 associated with registered users. Inaddition or as an alternative, users and user nodes 202 described hereinmay, where appropriate, refer to users that have not registered with thesocial-networking system. In particular embodiments, a user node 202 maybe associated with information provided by a user or informationgathered by various systems, including the social-networking system. Asan example and not by way of limitation, a user may provide their name,profile picture, contact information, birth date, sex, marital status,family status, employment, education background, preferences, interests,or other demographic information. In particular embodiments, a user node202 may be associated with one or more data objects corresponding toinformation associated with a user. In particular embodiments, a usernode 202 may correspond to one or more webpages. A user node 202 may beassociated with a unique user identifier for the user in thesocial-networking system.

In particular embodiments, a concept node 204 may correspond to aconcept. As an example and not by way of limitation, a concept maycorrespond to a place (such as, for example, a movie theater,restaurant, landmark, or city); a website (such as, for example, awebsite associated with the social-network service or a third-partywebsite associated with a web-application server); an entity (such as,for example, a person, business, group, sports team, or celebrity); aresource (such as, for example, an audio file, video file, digitalphoto, text file, structured document, or application) which may belocated within the social-networking system or on an external server,such as a web-application server; real or intellectual property (suchas, for example, a sculpture, painting, movie, game, song, idea,photograph, or written work); a game; an activity; an idea or theory;another suitable concept; or two or more such concepts. A concept node204 may be associated with information of a concept provided by a useror information gathered by various systems, including thesocial-networking system. As an example and not by way of limitation,information of a concept may include a name or a title; one or moreimages (e.g., an image of the cover page of a book); a location (e.g.,an address or a geographical location); a website (which may beassociated with a URL); contact information (e.g., a phone number or anemail address); other suitable concept information; or any suitablecombination of such information. In particular embodiments, a conceptnode 204 may be associated with one or more data objects correspondingto information associated with concept node 204. In particularembodiments, a concept node 204 may correspond to one or more webpages.

In particular embodiments, a node in social graph 200 may represent orbe represented by a webpage (which may be referred to as a “profilepage”). Profile pages may be hosted by or accessible to thesocial-networking system. Profile pages may also be hosted onthird-party websites associated with a third-party server. As an exampleand not by way of limitation, a profile page corresponding to aparticular external webpage may be the particular external webpage andthe profile page may correspond to a particular concept node 204.Profile pages may be viewable by all or a selected subset of otherusers. As an example and not by way of limitation, a user node 202 mayhave a corresponding user-profile page in which the corresponding usermay add content, make declarations, or otherwise express himself orherself. A business page such as business page 205 may comprise auser-profile page for a commerce entity. As another example and not byway of limitation, a concept node 204 may have a correspondingconcept-profile page in which one or more users may add content, makedeclarations, or express themselves, particularly in relation to theconcept corresponding to concept node 204.

In particular embodiments, a concept node 204 may represent athird-party webpage or resource hosted by a third-party system. Thethird-party webpage or resource may include, among other elements,content, a selectable or other icon, or other inter-actable object(which may be implemented, for example, in JavaScript, AJAX, or PHPcodes) representing an action or activity. As an example and not by wayof limitation, a third-party webpage may include a selectable icon suchas “like,” “check in,” “eat,” “recommend,” or another suitable action oractivity. A user viewing the third-party webpage may perform an actionby selecting one of the icons (e.g., “eat”), causing a client system tosend to the social-networking system a message indicating the user'saction. In response to the message, the social-networking system maycreate an edge (e.g., an “eat” edge) between a user node 202corresponding to the user and a concept node 204 corresponding to thethird-party webpage or resource and store edge 206 in one or more datastores.

In particular embodiments, a pair of nodes in social graph 200 may beconnected to each other by one or more edges 206. An edge 206 connectinga pair of nodes may represent a relationship between the pair of nodes.In particular embodiments, an edge 206 may include or represent one ormore data objects or attributes corresponding to the relationshipbetween a pair of nodes. As an example and not by way of limitation, afirst user may indicate that a second user is a “friend” of the firstuser. In response to this indication, the social-networking system maysend a “friend request” to the second user. If the second user confirmsthe “friend request,” the social-networking system may create an edge206 connecting the first user's user node 202 to the second user's usernode 202 in social graph 200 and store edge 206 as social-graphinformation in one or more data stores. In the example of FIG. 2, socialgraph 200 includes an edge 206 indicating a friend relation between usernodes 202 of user “Amanda” and user “Dorothy.” Although this disclosuredescribes or illustrates particular edges 206 with particular attributesconnecting particular user nodes 202, this disclosure contemplates anysuitable edges 206 with any suitable attributes connecting user nodes202. As an example and not by way of limitation, an edge 206 mayrepresent a friendship, family relationship, business or employmentrelationship, fan relationship, follower relationship, visitorrelationship, subscriber relationship, superior/subordinaterelationship, reciprocal relationship, non-reciprocal relationship,another suitable type of relationship, or two or more suchrelationships. Moreover, although this disclosure generally describesnodes as being connected, this disclosure also describes users orconcepts as being connected. Herein, references to users or conceptsbeing connected may, where appropriate, refer to the nodes correspondingto those users or concepts being connected in social graph 200 by one ormore edges 206.

In particular embodiments, an edge 206 between a user node 202 and aconcept node 204 may represent a particular action or activity performedby a user associated with user node 202 toward a concept associated witha concept node 204. As an example and not by way of limitation, asillustrated in FIG. 2, a user may “like,” “attended,” “played,”“listened,” “cooked,” “worked at,” or “watched” a concept, each of whichmay correspond to a edge type or subtype. A concept-profile pagecorresponding to a concept node 204 may include, for example, aselectable “check in” icon (such as, for example, a clickable “check in”icon) or a selectable “add to favorites” icon. Similarly, after a userclicks these icons, the social-networking system may create a “favorite”edge or a “check in” edge in response to a user's action correspondingto a respective action. As another example and not by way of limitation,a user (user “Carla”) may listen to a particular song (“Across the Sea”)using a particular application (SPOTIFY, which is an online musicapplication). In this case, the social-networking system may create a“listened” edge 206 and a “used” edge (as illustrated in FIG. 2) betweenuser nodes 202 corresponding to the user and concept nodes 204corresponding to the song and application to indicate that the userlistened to the song and used the application. Moreover, thesocial-networking system may create a “played” edge 206 (as illustratedin FIG. 2) between concept nodes 204 corresponding to the song and theapplication to indicate that the particular song was played by theparticular application. In this case, “played” edge 206 corresponds toan action performed by an external application (SPOTIFY) on an externalaudio file (the song “Across the Sea”). Although this disclosuredescribes particular edges 206 with particular attributes connectinguser nodes 202 and concept nodes 204, this disclosure contemplates anysuitable edges 206 with any suitable attributes connecting user nodes202 and concept nodes 204. Moreover, although this disclosure describesedges between a user node 202 and a concept node 204 representing asingle relationship, this disclosure contemplates edges between a usernode 202 and a concept node 204 representing one or more relationships.As an example and not by way of limitation, an edge 206 may representboth that a user likes and has used at a particular concept.Alternatively, another edge 206 may represent each type of relationship(or multiples of a single relationship) between a user node 202 and aconcept node 204 (as illustrated in FIG. 2 between user node 202 foruser “Edwin” and concept node 204 for “SPOTIFY”).

In particular embodiments, the social-networking system may create anedge 206 between a user node 202 and a concept node 204 in social graph200. As an example and not by way of limitation, a user viewing aconcept-profile page (such as, for example, by using a web browser or aspecial-purpose application hosted by the user's client system) mayindicate that he or she likes the concept represented by the conceptnode 204 by clicking or selecting a “Like” icon, which may cause theuser's client system to send to the social-networking system a messageindicating the user's liking of the concept associated with theconcept-profile page. In response to the message, the social-networkingsystem may create an edge 206 between user node 202 associated with theuser and concept node 204, as illustrated by “like” edge 206 between theuser and concept node 204. In particular embodiments, thesocial-networking system may store an edge 206 in one or more datastores. In particular embodiments, an edge 206 may be automaticallyformed by the social-networking system in response to a particular useraction. As an example and not by way of limitation, if a first useruploads a picture, watches a movie, or listens to a song, an edge 206may be formed between user node 202 corresponding to the first user andconcept nodes 204 corresponding to those concepts. Although thisdisclosure describes forming particular edges 206 in particular manners,this disclosure contemplates forming any suitable edges 206 in anysuitable manner.

The social graph 200 may further comprise a plurality of product nodes.Product nodes may represent particular products that may be associatedwith a particular business. A business may provide a product catalog tothe consumer-to-business service 110 and the consumer-to-businessservice 110 may therefore represent each of the products within theproduct in the social graph 200 with each product being in a distinctproduct node. A product node may comprise information relating to theproduct, such as pricing information, descriptive information,manufacturer information, availability information, and other relevantinformation. For example, each of the items on a menu for a restaurantmay be represented within the social graph 200 with a product nodedescribing each of the items. A product node may be linked by an edge tothe business providing the product. Where multiple businesses provide aproduct, each business may have a distinct product node associated withits providing of the product or may each link to the same product node.A product node may be linked by an edge to each user that has purchased,rated, owns, recommended, or viewed the product, with the edgedescribing the nature of the relationship (e.g., purchased, rated, owns,recommended, viewed, or other relationship). Each of the product nodesmay be associated with a graph id and an associated merchant id byvirtue of the linked merchant business. Products available from abusiness may therefore be communicated to a user by retrieving theavailable product nodes linked to the user node for the business withinthe social graph 200. The information for a product node may bemanipulated by the social-networking system as a product object thatencapsulates information regarding the referenced product.

FIG. 3A illustrates a user interface 300 with a message interactiondisplay 310 with messaging bot invocation controls 315.

A client device 320 may correspond to any device used to access aconsumer-to-business messaging system 100. While in the illustratedembodiment of FIG. 3A the client device 320 resembles a smartphonedevice, it will be appreciated that the techniques described herein maybe used with any type of device. The user interface 300 may generallycorrespond to a display of a user inbox for the messaging system 140.

A messaging client may display a messaging client header 305. Themessaging client header 305 may comprise a title for a message thread,such as the name of one or more users participating in the messagethread, which may be selected according to real name, nick names, orother name information. The messaging client header 305 may comprise acontrol to return a user to an inbox view for the messaging client. Aninbox view control may be augmented with a number of recent messagethreads with unread messages.

The user interface 300 for a message thread may include compositioncontrols 322. Many, most, or nearly all of the composition controls 322may empower access to and use of interface controls for the performanceof various tasks, such as text entry, media selection, emoji selection,camera use, a social approval icon, etc. The controls may include textentry controls empowering the entering of text for the composition oftext-based messages. The controls may include hardware controls. In someembodiments, controls may be touchscreen-based controls.

The user interface 300 for the message thread may comprise a messageinteraction display 310. The message interaction display 310 maycomprise the messages exchanged within the message thread. The messageinteraction display 310 may be iteratively updated as additionalmessages are added to the message thread by the participants in themessage thread. Messages may be displayed in association with an avatarfor the user.

A messaging client and/or messaging system 140 may detect an element foruse in selecting and configuring one or more messaging bots. Anextracted element 312 may generally correspond to a word, phrase, orother element of a message thread that a messaging system 140 associateswith a potential action, option, or other suggestion. The messagingsystem 140 using an extracted element 312 may invoke suggested services,such as suggested messaging bots, related to the extracted element 312.Elements for extraction may be determined based on predetermined andpre-assigned associations between words and/or phrases and varioussuggestions, or may be automatically determined based on naturallanguage programming techniques.

The extracted element 312, or any other content or context of a messagethread, may invoke the display of messaging bot invocation controls 315.The messaging client may retrieve and display a plurality of suggestedservices, such as may correspond to suggests messaging bots, in aplurality of triggered messaging bot invocation controls 315. In someembodiments, the plurality of suggested services may be automaticallydisplayed on response to the messaging client and/or messaging system140 detecting a relevant context, such as based on an extracted element312 or a plurality of extracted elements. The messaging bot invocationcontrols 315 may comprise a plurality of messaging bot options. Amessaging bot invocation control may comprise a particular messaging botassociated with a particular service.

The messaging bot invocation controls 315 may comprise suggestions forservices, as may be represented by messaging bots. The messaging botinvocation controls 315 may comprise a ranked list of suggestedmessaging bots. Suggested messaging bots may be determined based on avariety of techniques and based on a variety of factors. Suggestedmessaging bots may be selected and ranked based on the location of theuser(s) in the thread. Messaging bots that relate to activities thathave previously been associated with a user's current geographiclocation may similarly be selected or ranked higher, such as suggestingrestaurant-related messaging bots when a couple are messaging each otherwhile both are at their place of employment. The ranking of thesuggested messaging bots may be represented in the ordering of themessaging bot invocation controls 315, with higher-ranked messaging botsdisplayed more prominently and lower-ranked messaging bots displayedless prominently. For instance, some lower-ranked messaging bots may bearranged such that they are completely or partially off-screen and onlyrevealed (or fully revealed) if the user navigations through themessaging bot invocation controls 315.

Suggested messaging bots may be selected and ranked based onassociations between one or more detected keywords or intents and themessaging bots. A keyword may correspond to a word or phrase extractedfrom the contents of a messaging interaction. The messaging system 140may have a registry of relevant keywords and may examine the contents ofmessaging interactions to identify and extract those keywords as a basisfor selecting and ranking messaging bots. For example, a mention of“ride” or “transport” may prompt the suggestion oftransportation-related service or a higher ranking fortransportation-related services. An intent may comprise a keyword,concept, phrase, or other identifier generated based on the context of amessaging interaction distinct from merely extracting a word or phrasefrom the messaging interaction. The messaging system 140 may have aregistry of intents and may perform natural language processing on thecontents of a messaging interaction to determine intents inferred by themessaging interaction. For example, a mention of multiple specificmovies may imply the intent keyword “movie” without a specific use ofthe word “movie.” In another example, a person-to-person inquiryregarding whether they “want to go see something” could imply aninterest in movies without the direct use of the word “movie.” As such,the messaging system 140 may generate an intent for a messaginginteraction that includes words or phrases not used in the messaginginteraction.

Keywords and/or intent may be extracted from the content, or a portionof the content, of the messaging interaction embodied in a messagethread. In some cases, a recent portion of the message thread may beused, such as by detecting a current period of engagement with themessage thread and extracting keywords and/or intent from the messagethread for that current period. The recent portion of a message threadmay be defined according to a variety of techniques. In some cases, therecent portion may be defined according to a predefined length of time,with the recent portion being the segment of the thread exchanged duringan extent of time spanning a length equal to the predefined length oftime and concluding at the current time. In some cases, the recentportion may be determined as spanning a variable length, such as bydetecting the most recent break in conversation of sufficient length,which may be predefined, to indicate temporary disengagement with themessage thread. For example, the recent portion of the message threadmay be the maximum extent of the thread concluding at the current timethat does not include any gap in conversation longer than one hour.Other techniques for defining a recent portion of a thread may be used.This recent portion of the message thread may be analyzed to determineone or more keywords, which may comprise one or more explicit keywordsexplicitly used within the message thread and which may comprise one ormore intent keywords inferred from the message thread based on naturallanguage processing techniques.

Keywords, whether explicitly extracted or derived from intent, may beused to determine one or more services that may be of interest to theuser(s) in the message thread. The messaging bot invocation controls 315may comprise a selection of messaging bots corresponding to one or moreproviders for the one or more services. For instance, keywords relatedto “dinner” and “food” may be extracted or inferred. A plurality ofproviders related to dinning may be selected, such as areservation-procurement service and a menu-listing service. Relatedservices may also be selected, such as a ride-sharing service fortransportation to a restaurant. The plurality of providers for each ofthe plurality of services may be joined together into a plurality ofcombined providers representing the plurality of services detected asbeing of possible interne to the user(s) in the message thread. Thisplurality of combined providers, and their associated messaging bots,may then be ranked according to a variety of factors, includinglocation, level of detected interest in the services provided by theproviders, level of detected interest in the specific providers,previous history of requesting various services either globally for theone or more user(s) or specifically within the message thread, previoushistory of using various providers either globally for the one or moreuser(s) or specifically within the message thread, or according to anyother relevant factor.

In some embodiments, where multiple services are to be offered, theranking of the corresponding providers may be constructed so as toshowcase the variety of services being offered. For instance, ahighest-ranked provider for each service may be selected and offered asthe top-listed provider (and therefore a top-listed associated messagingbot) prior to a second provider for any of the services. Thehighest-ranked provider for each service may be ranked according topredicted interest in the service in general and/or based on thepredicted interest in the provider specifically, such as may bedetermined according to various factors described herein.

Selecting a messaging bot invocation control of the plurality ofmessaging bot invocation controls 315 may invoke an interface forinteraction with that particular selected messaging bot.

In some embodiments, a message thread may be a multi-user message threadin which multiple participants engage in a message interaction. However,in an alternative embodiment, the message thread may be a bot-requestthread in which a user engages directly and purposefully with a systemthat can recommend and guide the user to various messaging bots. A usermay select a bot-request thread from a list of bots, engage with abot-request engine to receive recommended bots, and then engage with thebots in the bot-request thread. For example, rather than asking “Want toget dinner tonight? I'm thinking Chinese food.” a user might submit “I'dlike to get dinner tonight and am thinking Chinese food.” in thebot-request thread, with the bot-request system determining the userintent and recommending messaging bots to the user. The messaging botinvocation controls 315 may then be presented, not as a response to thedetection of an opportunity for recommendations implicit in auser-to-user interaction, but instead as a response to a direct query bythe user.

In another alternative embodiment, a request for assistance from amessaging bot may be directly invoked within a user-to-user messagethread. A bot request may be made by directly addressing thebot-suggestion system. Directly addressing the bot-suggestion system maybe performed using a variety of techniques. For instance, thebot-suggestions system may be addressed by prefixing a text-basedrequest with a text segment indicating that the bot-suggestion system isbeing addressed. For example, a user might enter “@M I'd like to getdinner tonight and am thinking Chinese food,” with the “@M” text segmentinvoking the bot-suggestion system. Alternatively or additionally, acontrol may be provided as part of the composition controls 322empowering addressing of the bot-suggestion system with the user-to-usermessage thread. In some embodiments, where the bot-suggestion system isdirectly invoked, the invocation of the bot-suggestion system, anyresponses by the bot-suggestion system (such as messaging bot invocationcontrols 315 or other responses), or interactions with the messaging botmay only be shown to the user of the client device 320 that invokes thebot-suggestion system and any bots, with the messaging system 140refraining from providing these interactions to other client devices.This creates a side-conversation within a user-to-user message threadbetween the invoking user and the bot-suggestion system and messagingbots that is private from any other participants in the thread. However,in other embodiments, other client devices, and therefore their users,may be provided some or all of these interactions.

FIG. 3B illustrates a user interface 325 with a messaging bot menu 335.

A messaging bot menu 335 for a particular messaging bot may be displayedin response to a messaging bot invocation control for that messaging botbeing selected by a user of a client device 320. The messaging bot menu335 may be displayed in association with the messaging thread from whichit is invoked.

The messaging bot menu 335 is a display element specifically associatedwith a particular messaging bot and empowers a user to interact with aninterface for the messaging bot within the context of the message threadfrom which it is invoked. The user of the client device 320 may moveinto the messaging bot menu 335, interact with the messaging bot menu335 to interact with the messaging bot, back out of the messaging botmenu 335 to re-engage with the messaging conversation in the messagethread, move back into the messaging bot menu 335 to re-engage with themessaging bot, move between different messaging bot menus, and generallydynamically interact with messaging bot menus within the context of themessage thread so as to select and interact with a messaging bot whileretaining a connection to an ongoing messaging conversation.

Messaging bot invocation controls 330 may be displayed adjacent to themessaging bot menu 335. The messaging bot invocation controls 330 may besubstantially similar to the messaging bot invocation controls 315displayed adjacent to a messaging conversation, but relocated to a topportion of the screen of the client device 320. The relocated messagingbot invocation controls 330 may be tabs for selecting between thevarious messaging bot menus. As such, selecting a currently-unselectedmessaging bot invocation control may transition the messaging client todisplay the messaging bot menu for the now-selected messaging botinvocation control. The particular messaging bot invocation controlassociated with the current messaging bot menu 335 may be displayed witha distinct visual style, so as to indicate that the messaging bot forthat messaging bot invocation control currently has the active messagingbot menu 335. Re-selecting the control for the currently-activemessaging bot menu 335 may minimize the messaging bot menu 335 toempower the user to return to the view of the messaging bot conversationin a messaging interaction display 310.

The messaging bot menu 335 may comprise a plurality of customizationoptions 345. These customization options 345 comprise settingsconfiguring a messaging bot as set by controls for the messaging botprovided as part of the messaging bot menu 335. Customization options345 may be initially set automatically based on the context of themessage thread, based on the content of the specific messaginginteraction prompting the display of the messaging bot invocationcontrols 315, based on user information for the message thread and/orthe specific messaging interaction, and/or according to other analysisof the context of the messaging bot menu 335. These customizationoptions 345 may then be retained by the user or modified using thecontrols of the messaging bot menu 335.

In general, the messaging bot menu 335 is configured based on thecustomization options 345, whether customization options 345 setautomatically or set manually by the user of the client device 320. Insome instances, a messaging bot menu 335 may include one or more menuentries. For example, for a messaging bot menu 335 designed forconfiguring, displaying, and selecting restaurant recommendations, amenu entry 340 may correspond to a particular restaurant. A menu entry340 may include a name, location, pricing information, performanceinformation, and other information relating to the menu entry 340. Amenu entry 340 may include one or more controls. For example, a controlfor a restaurant menu may empower the selection of both a restaurant anda particular available reservation time for the restaurant. In theseinstances, the menu entries are determined at least in part based on thecustomization options 345. The menu entries may also be determined inpart on additional information, such as information relating to amessage thread or participants in a message thread.

FIG. 3C illustrate a user interface 350 for an updated messaging botmenu 360 with updated customization options 370.

An updated messaging bot menu 360 is generated to replace a previousmessaging bot menu 335 when a user configures updated customizationoptions 370. In some cases, at least a portion of theautomatically-configured customization options 345 may differ from auser's preferences. For example, the messaging system 140 may inform themessaging bot as to a number of participants in a message thread, whichmay effect an automatically-configured number of people set as acustomization option equal to the number of participants. However, auser may determine that a lesser number of people (e.g., only a portionof the messaging participants) or greater number of people (e.g.,including additional people) should be included and generate updatedcustomization options 370. More generally, any customization options maybe modified to generate updated customization options 370. These updatedcustomization options 370 may be provided to the messaging bot togenerate an updated messaging bot menu 360 reflecting the updatedcustomization options 370. An updated messaging bot menu 360 may includemodified menu entries, such as recommendations. However, in some cases,the menu entries may remain the same, with the updated customizationoptions 370 being retained and used to configure a requested service,such as where the same menu entries are shown independent of the numberof people a restaurant reservation would be for.

FIG. 3D illustrate a user interface 375 for a messaging bot menu 380 fora different messaging bot with customization options 385 carried overbetween messaging bots.

The illustrated embodiment of FIG. 3D may correspond to a user havingselected a different messaging bot invocation control of the pluralityof messaging bot invocation controls 330: a different messaging botinvocation control than a currently-selected control. This willtransition the distinct visual style indicating which indicates thecurrently-active messaging bot to the now-selected messaging bot.

A replacement messaging bot menu 380 replaces the previous messaging botmenu 360 with messaging bot content related to the now-selectedmessaging bot. This messaging bot menu 380 may also containcustomization options 385 for configuring the now-selected messagingbot. These customization options 385 may be set based on not only themessage thread and message participant information, but also any usermodifications made to the previous customization options. For instance,when a user generates updated customization options 370, any changesrepresented in the updated customization options 370 are carried over tothe customization options 385 for the replacement messaging bot menu380. The messaging system 140 records the user-specified customizationoptions and provides them to the replacement messaging bot ascustomization options 385 for use with the replacement messaging bot.This may serve as a convenience to the user of the client device 320 byeliminating a duplicate setting of a particular setting for thecustomization options for the replacement messaging bot menu 380 thatwas already set in the previous messaging bot menu 360.

FIG. 4A illustrates a user interface 400 for a messaging bot menu 410for a configured service request. A messaging bot menu 410 may advanceto a point where a service request has been sufficiently configured asto allow a service request. Once the messaging bot menu 410 has reachedthis state, a service request control 415 may be displayed. However, insome cases, a user may select the messaging bot invocation control forthe current messaging bot menu 410 and minimize the messaging bot menu410 in order to engage with the messaging interaction of a messagethread.

FIG. 4B illustrates a user interface 425 for a message interactiondisplay 430 with persistent messaging bot invocation controls 435. FIG.4B may correspond to the state of the client device 320 after a user hasselected a messaging bot invocation control for a current messaging botmenu and minimized the messaging bot menu in order to engage with themessaging interaction of a message thread via a message interactiondisplay 430. The messaging interaction display 430 may include themessaging bot invocation controls 435 to empower a return to themessaging bot menus. The composition controls 440 may be returned toempower engagement with the messaging interaction.

FIG. 4C illustrates a user interface 450 with a restored messaging botmenu 460. The restored messaging bot menu 460 restores a user's place ina messaging bot menu that was configured and then minimized through themessaging bot invocation controls 455. The restored messaging bot menu460 may be retrieved by selecting the messaging bot in a displayed setof the messaging bot invocation controls 455. A service request control415 may be displayed as part of the restored messaging bot menu 460. Anystate of a restored messaging bot menu 460 may be saved on the clientdevice 320 and then retrieved when a messaging bot invocation controlwith an associated save messaging bot menu is selected.

FIG. 4D illustrates a user interface 475 with a message interactiondisplay 480 with administrative text 485 communication a servicerequest. Once a user has selected a service request control 415, orotherwise requested a service from a messaging bot, the messaging botmay provide administrative text 485 to the messaging system 140, theadministrative text 485 communicating the configured service. Theadministrative text 485 is then provided by the messaging system 140 tothe client device 320 for display as part of the messaging interactiondisplay 480. The administrative text 485 may also be distributed toother client devices belonging to the user and to client devicesassociated with other participants in the message thread. Theadministrative text 485 may include text, images, controls, or any otherelement. The administrative text 485 may be customized based on theviewer. For example, the administrative text may identify the userrequesting a service differently to that user and to other users

FIG. 5 illustrates a determination of a user intent based on a messaginginteraction.

A messaging system 140 may comprise a plurality of components. In someembodiments, these plurality of components may be distributed among aplurality of servers. In other embodiments, a single server mayimplement the plurality of components. In some embodiments, a pluralityof servers may be executed by a single server device. In otherembodiments, the plurality of servers may be executed by a plurality ofserver devices. In some embodiments, multiple instances of the variouscomponents and various servers may be executed to provide redundancy,improved scaling, and other benefits. Similarly, a client device mayexecute a plurality of components as part of a messaging client.

A client device may communicate with other devices using wirelesstransmissions to exchange network traffic. Exchanging network traffic,such as may be included in the exchange of messaging transactions, maycomprise transmitting and receiving network traffic via a networkinterface controller (NIC). A NIC comprises a hardware componentconnecting a computer device, such as client device, to a computernetwork. The NIC may be associated with a software network interfaceempowering software applications to access and use the NIC. Networktraffic may be received over the computer network as signals transmittedover data links. The network traffic may be received by capturing thesesignals and interpreting them. The NIC may receive network traffic overthe computer network and transfer the network traffic to memory storageaccessible to software applications using a network interfaceapplication programming interface (API). The network interfacecontroller may be used for the network activities of the embodimentsdescribed herein, including the interoperation of the messaging clientand messaging servers through network communication. For example, themessaging client transmitting or receiving messages to or from a clientfront-end server 535 may be interpreted as using the network interfacecontroller for network access to a communications network for thetransmission or reception of information.

A messaging client may comprise a user interface component 523. A userinterface component 523 may be generally arranged to display userinterfaces to a user of a client device and to receive user commands forthe messaging client for the client device. A messaging client maycomprise a client messaging component 526. A client messaging component526 may be generally arranged to conduct messaging interactions on thebehalf of the messaging client via communication with the clientfront-end server 535.

A client front-end server 535 may be generally arranged to act as anetwork access point to the messaging system 140 for client devices suchas sender client device 520. The client front-end server 535 maycomprise a messaging component 530, the messaging component 530generally arranged to act as a network access point to messagingservices for the messaging system 140. The messaging component 530 mayreceive messages from client devices and add the messages to messagequeues.

A message queue 580 may be specifically associated with the user ofsender client device 520, such as by being uniquely associated withinthe messaging system 140 with a user account for the user of senderclient device 520. The message queue 580 may be a single queue used forall messaging endpoints used by this user. The message queue 580 maycomprise a representation of updates in a strict linear order. Themessage queue 580 may be organized as a data unit according to a varietyof techniques. The message queue 580 may be stored in semi-persistentmemory, persistent storage, both semi-persistent memory and persistentstorage, or a combination of the two. The message queue 580 may beorganized according to a variety of data structures, including linkedlists, arrays, and other techniques for organizing queues. The messagequeue 580 may generally comprise a first-in-first-out (FIFO) queue inwhich no update will be removed or retrieved from the queue before anyupdates that were received prior to it.

The messaging system 140 may comprise one or more worker servers, suchas worker servers 545, 555, 565. In general, the messaging system 140may comprise a plurality of worker servers that may be assigned tovarious tasks. A worker server 545 may comprise a message queuemonitoring component 540, the message queue monitoring component 540arranged to monitor updates, such as may comprise messages, in themessage queue 580 and other message queues of the messaging system 140for various flags, indicators, and other information. A worker server 55may comprise an interaction processing component 550, the interactionprocessing component 550 operative to manage the generation of a userintent 515 based on the contents of a messaging interaction. A workerserver 565 may comprise a natural-language machine learning component560, the natural-language machine learning component 560 operative touse natural-language processing (NLP) techniques using machine learningto analyze messaging interactions and generate user intent 515 based onthe messaging interactions.

The interaction processing component 550 may interface with anatural-language machine learning (NLML) component 560. The NLMLcomponent 560 analyzes the contents of a messaging interaction todetermine an intent of the messaging interaction. The intent representsa goal being sought to by the messaging interaction. For instance,people discussing where to get dinner may have an intent of “dinning,”“eating,” “restaurant,” or other related term. The interactionprocessing component 550 may provide the content of a messaginginteraction, including one or more messages, to the NLML component 550and the NLML component 550 replies with the user intent 515, or multipleuser intents, it detects for that interaction. The NLML component 550may be implemented using known natural language processing (NLP) andmachine learning (ML) techniques.

The message queue monitoring component 540 monitors a messaginginteraction. This messaging interaction is exchanged via a messagingsystem 140. This messaging interaction involving at least one clientdevice, such as a sender client device 520 and/or a recipient clientdevice 590. A message 510 may be sent from a client messaging component526 of a messaging client on a sender client device 520. This message510 is associated with a message thread, the message thread involvingtwo or more participants, including the user of the sender client device520. This message 510 comprises a portion of the messaging interactionof a message thread.

The message 510 is received by the messaging component 530 of the clientfront-end server 535 and is added to a message queue 580 associated withthe sender. The message 510 is distributed using the message queue 580to the recipient client device 590. The message queue monitoringcomponent 540 also receives the message 510 and provides it to theinteraction processing component 550.

The interaction processing component 550 provides the message 510 to theNLML component 560 and receives the user intent 515 in response. Themessage 510 may be provided to the NLML component 560 as part of arepository of multiple messages, so as to empower the analysis of amessaging interaction as a whole. As such, the interaction processingcomponent 550 determines determine a user intent for the messaginginteraction by submitting at least a portion of the messaginginteraction to a NLML component 560 and receiving the user intent 515from the NLML component 560 in response to submitting at least theportion of the messaging interaction to the NLML component 560. Theinteraction processing component 550 may therefore detect the userintent 515 for the messaging interaction by using the NLML component560.

FIG. 6 illustrates a messaging bot options configuration 610 based on auser intent 515.

In some embodiments, a consumer-to-business messaging system 100 mayinclude a bot management component 660 that acts as an access point tomessaging bot services for the consumer-to-business messaging system100. The bot management component 660 may act as an intermediary betweenthe servers of the messaging system 140 and one or more internal and/orexternal bot execution servers. The bot management component 660 maycomprise a bot framework generally arranged to provide an accessibleframework to the messaging bot system. The bot management component 660may be executed by a worker server 665 substantially similar to theworker servers 545, 555, 565 described with reference to FIG. 5.

In some cases, messaging bots may be executed by servers external to theconsumer-to-business messaging system 100, such as an external botserver operated by the service associated with the bot. A bot managementcomponent 660 may determine an external bot server for the serviceassociated with the messaging bot. The bot management component 660 maysubmit messages to the messaging bot by sending the messages to theexternal bot server associated with the messaging bot. In someembodiments, submitting messages may comprise extracting message contentand transmitting the message content to the external bot server using abot server interaction application programming interface (API). Botmessages from the messaging bots may similarly be received by the botmanagement component 660 from an external bot server.

In other cases, messaging bots may be executed by the servers of theconsumer-to-business messaging system 100. The bot management component660 may determine a hosted bot server for the service associated with amessaging bot. A hosted bot server may comprise a bot server maintainedby the provider of the consumer-to-business messaging system 100. Thebot management component 660 may submit messages to the messaging bot bysending the messages to the hosted bot server associated with themessaging bot and may receive messages from the messaging bot byreceiving them from the hosted bot server.

The bot management component 660 receives the user intent 515 from theinteraction processing component 550 and determines a messaging botoptions configuration 610 for the client device based on the user intent515. The messaging bot options configuration 610 configures one or moreclient devices with interface controls empowering the one or more usersof the one or more client devices to engage with one or more messagingbots.

The bot management component 660 then sends the messaging bot optionsconfiguration 610 to the sending client device 520 in response to thechange in the context of the messaging interaction enacted by themessage 510 being sent by the sender client device 520. Sending themessaging bot options configuration 610 to the sender client device 520may comprise adding the messaging bot options configuration 610 to amessage queue 580, such as a message queue 580 associated with a messagethread in which the messaging interaction is occurring. The messagingbot options configuration is then distributed to the sender clientdevice 520 by a server messaging component 530 retrieving the messagingbot options configuration 610 from the message queue 580 and deliveringit to the client messaging component 526. The messaging bot optionsconfiguration 610 may be distributed to every user and client deviceinvolved in the messaging interaction, such as every client devicebelonging to every participant in the message thread. As such, arecipient client device 590 for the message 510 may also receive themessaging bot options configuration 610 generated in response to themessage 510.

A messaging interaction comprises a plurality of exchanged messages.This plurality of exchanged messages includes a most-recent message 510of the message interaction. A message package sent to the client devicevia the messaging component 530, with this message package associatedwith the most-recent message 510, may be used to deliver the messagingbot options configuration 610. A message package sent to the senderclient device 510 may be used to confirm receipt of the message 510 bythe messaging system 140, may be used to report delivery of the message510 to one or more recipient users, and/or may be used to report that arecipient user has viewed the message 510. A message package sent to arecipient client device 590 may comprise both the message 510, as may bethe initial delivery of the message 510 to the recipient client device590. In either case, the message package may additionally include themessaging bot options configuration 610.

In general, the message 510 may be sent to every client device relatedto a message thread, including the client device used to send themessage 510. This message 510 may be augmented in the package used todeliver the message 510 with the messaging bot options configuration610. The messaging bot options configuration 610 configures themessaging interface for the messaging client in displaying a messagethread with controls empowering interactions with a messaging bot.Therefore, the bot management component 660 is operative to send amessage package to the client device, the message package associatedwith the most-recent message 510, such that the message packagecomprises the messaging bot options configuration 610. This messagepackage updates the client device with the most-recent message 510. Insome cases, this most-recent message 510 is received from a differentclient device than the one receiving the message package. In some cases,the message package 510 may acknowledge receipt of the most-recentmessage from the client device.

In some instances, the messaging bot options configuration 610 may be amessaging bot menu associated with a messaging bot. The messaging botmenu is customized based on the user intent 515. The messaging bot menumay consist of a plurality of user-customizable options. Customizing themessaging bot menu based on the user intent may consist of pre-fillingone or more of the user-customizable options based on the user intent.The messaging bot menu may comprise a later stage or second stage ofproviding messaging bot options configurations to a client device, witha first stage being messaging bot options configurations and the secondstage being a customized messaging bot menu provided in response to anactivation of a messaging bot invocation control.

In some cases, customizing the messaging bot menu based on the userintent 515 may comprise selecting a menu section of the menu for displayon the client device based on the user intent 515. A messaging bot menumay be divided into sections. For example, a messaging bot menurepresenting a food menu for a restaurant may have sections fordifferent ingredients, kind of cuisine, or other considerations. In somecases, the restaurant may explicitly configure these sections whencreating a messaging bot. In other cases, the restaurant may provideingredient information (or, more generally, menu item information), withthe consumer-to-business messaging system 100 generating the menusections. A menu section may be automatically selected based on thecontext of the messaging interaction. For example, a user profile for auser may indicate that they are vegetarian or prefer vegetarian options.In response, the bot management component 660 may configure themessaging bot options configuration 610 to select a vegetarian menusection based on the user profile information. In another example, usersdiscussing seeing a movie may be presented with a section for a movieticket messaging bot, or other relevant messaging bot, that presents aspecific movie being discussed, a type of movie being discussed, orotherwise relates to the discussion.

In some instances, the messaging bot options configuration 610 mayconsist of a plurality of messaging bot invocation controls. Each of themessaging bot invocation controls is associated with a differentmessaging bot. This plurality of messaging bot invocation controls isselected based on the user intent 515. The user intent 515 may reflect auser-expressed goal or subject of a messaging interaction. Variousmessaging bots may be associated with this user intent 515. Forinstance, messaging bots may be assigned one or more user intents duringa registration with the consumer-to-business messaging system 100. Aplurality of messaging bots associated with the user intent 515 aredetermined and provided to a client device. In some instances, theplurality of messaging bot invocation controls may be additionallyselected based on a user context. A user context may consist of one ormore of a user location and a local user time, without limitation. Theplurality of messaging bot invocation controls may additionally beselected based on a user profile, such as based on user servicepreference information stored in the user profile.

After the delivery of a messaging bot options configuration 610comprising messaging bot invocation controls, the user of the clientdevice may select one of the messaging bot invocation controls. Themessaging component 550 may then receive a user messaging bot selectionof a selected messaging bot invocation control of the plurality ofmessaging bot invocation controls from the client device. A selectedmessaging bot invocation control is associated with a selected messagingbot. The user messaging bot selection is passed to the bot managementcomponent 660, which then sends a messaging bot interface to the clientdevice in response. This messaging bot interface may comprise, in someinstances, a messaging bot menu.

To process the messaging bot selection, the bot management component 660sends a messaging bot invocation message to a bot server associated withthe selected messaging bot. The messaging bot invocation messageincludes the user intent 515 to empower the messaging bot to configureitself according to the user intent 515. In some instances, the botserver may be hosted by the consumer-to-business messaging system 100.In other instances, the bot server may be externally hosted, such as bythe developer of the messaging bot. The bot management component 660then receives a messaging bot interface specification from the botserver in response to the messaging bot invocation message, where thismessaging bot interface is based on the messaging bot interfacespecification.

A messaging bot interface may comprise a plurality of user-customizableoptions. The consumer-to-business messaging system 100 may receive oneor more user option configurations for the plurality ofuser-customizable options based on a user configuration one or moreuser-customizable options. The consumer-to-business messaging system 100may then receive a second user messaging bot selection of a secondmessaging bot invocation control of the plurality of messaging botinvocation controls from the client device, the second selectedmessaging bot invocation control associated with a second selectedmessaging bot distinct from the selected messaging bot. Theconsumer-to-business messaging system 100 then sends a second messagingbot interface to the client device in response to receiving theinvocation of the selected messaging bot invocation control, the secondmessaging bot interface associated with the second selected messagingbot. The consumer-to-business messaging system 100 thereby transitionsfrom displaying an interface for a first messaging bot to a secondmessaging bot. To ease this transition, the consumer-to-businessmessaging system 100 configures the second messaging bot interface basedon the one or more user option configurations. Configuring the secondmessaging bot interface based on the one or more user optionconfigurations thereby transitions the one or more user optionconfigurations to the second messaging bot interface. This storage andapplication of the one or more user option configurations may beperformed by either the user interface component 523 of the messagingclient or by the bot management component 660, depending on theembodiment.

Included herein is a set of flow charts representative of exemplarymethodologies for performing novel aspects of the disclosedarchitecture. While, for purposes of simplicity of explanation, the oneor more methodologies shown herein, for example, in the form of a flowchart or flow diagram, are shown and described as a series of acts, itis to be understood and appreciated that the methodologies are notlimited by the order of acts, as some acts may, in accordance therewith,occur in a different order and/or concurrently with other acts from thatshown and described herein. For example, those skilled in the art willunderstand and appreciate that a methodology could alternatively berepresented as a series of interrelated states or events, such as in astate diagram. Moreover, not all acts illustrated in a methodology maybe required for a novel implementation.

FIG. 7 illustrates one embodiment of a logic flow 700. The logic flow700 may be representative of some or all of the operations executed byone or more embodiments described herein.

In the illustrated embodiment shown in FIG. 7, the logic flow 700 maymonitor a messaging interaction, the messaging interaction exchanged viaa messaging system, the messaging interaction involving at least oneclient device at block 702.

The logic flow 700 may detect a user intent for the messaginginteraction at block 704.

The logic flow 700 may determine a messaging bot options configurationfor the client device based on the user intent at block 706.

The logic flow 700 may send the messaging bot options configuration tothe client device at block 708.

The embodiments are not limited to this example.

FIG. 8 illustrates a block diagram of a centralized system 800. Thecentralized system 800 may implement some or all of the structure and/oroperations for the consumer-to-business messaging system 100 in a singlecomputing entity, such as entirely within a single centralized serverdevice 820.

The centralized server device 820 may comprise any electronic devicecapable of receiving, processing, and sending information for theconsumer-to-business messaging system 100. Examples of an electronicdevice may include without limitation an ultra-mobile device, a mobiledevice, a personal digital assistant (PDA), a mobile computing device, asmart phone, a telephone, a digital telephone, a cellular telephone,ebook readers, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, television, digitaltelevision, set top box, wireless access point, base station, subscriberstation, mobile subscriber center, radio network controller, router,hub, gateway, bridge, switch, machine, or combination thereof. Theembodiments are not limited in this context.

The centralized server device 820 may execute processing operations orlogic for the consumer-to-business messaging system 100 using aprocessing component 830. The processing component 830 may comprisevarious hardware elements, software elements, or a combination of both.Examples of hardware elements may include devices, logic devices,components, processors, microprocessors, circuits, processor circuits,circuit elements (e.g., transistors, resistors, capacitors, inductors,and so forth), integrated circuits, application specific integratedcircuits (ASIC), programmable logic devices (PLD), digital signalprocessors (DSP), field programmable gate array (FPGA), memory units,logic gates, registers, semiconductor device, chips, microchips, chipsets, and so forth. Examples of software elements may include softwarecomponents, programs, applications, computer programs, applicationprograms, system programs, software development programs, machineprograms, operating system software, middleware, firmware, softwaremodules, routines, subroutines, functions, methods, procedures, softwareinterfaces, application program interfaces (API), instruction sets,computing code, computer code, code segments, computer code segments,words, values, symbols, or any combination thereof. Determining whetheran embodiment is implemented using hardware elements and/or softwareelements may vary in accordance with any number of factors, such asdesired computational rate, power levels, heat tolerances, processingcycle budget, input data rates, output data rates, memory resources,data bus speeds and other design or performance constraints, as desiredfor a given implementation.

The centralized server device 820 may execute communications operationsor logic for the consumer-to-business messaging system 100 usingcommunications component 840. The communications component 840 mayimplement any well-known communications techniques and protocols, suchas techniques suitable for use with packet-switched networks (e.g.,public networks such as the Internet, private networks such as anenterprise intranet, and so forth), circuit-switched networks (e.g., thepublic switched telephone network), or a combination of packet-switchednetworks and circuit-switched networks (with suitable gateways andtranslators). The communications component 840 may include various typesof standard communication elements, such as one or more communicationsinterfaces, network interfaces, network interface cards (NIC), radios,wireless transmitters/receivers (transceivers), wired and/or wirelesscommunication media, physical connectors, and so forth. By way ofexample, and not limitation, communication media 812 includes wiredcommunications media and wireless communications media. Examples ofwired communications media may include a wire, cable, metal leads,printed circuit boards (PCB), backplanes, switch fabrics, semiconductormaterial, twisted-pair wire, co-axial cable, fiber optics, a propagatedsignal, and so forth. Examples of wireless communications media mayinclude acoustic, radio-frequency (RF) spectrum, infrared and otherwireless media.

The centralized server device 820 may implement the consumer-to-businessservice 110 in a single computing entity. The centralized server device820 may communicate with other devices over a communications media 812using communications signals 814 via the communications component 840.The devices may be internal or external to the centralized server device820 as desired for a given implementation. The centralized server device820 may communicate with a plurality of client devices 810, such as maycomprise the client device 120, client device 320, sender client device520, recipient client device 590, or any other client device.

FIG. 9 illustrates a block diagram of a distributed system 900. Thedistributed system 900 may distribute portions of the structure and/oroperations for the consumer-to-business messaging system 100 acrossmultiple computing entities. Examples of distributed system 900 mayinclude without limitation a client-server architecture, a 3-tierarchitecture, an N-tier architecture, a tightly-coupled or clusteredarchitecture, a peer-to-peer architecture, a master-slave architecture,a shared database architecture, and other types of distributed systems.The embodiments are not limited in this context.

The distributed system 900 may comprise a plurality of distributedserver devices 910. In general, the distributed server devices 910 maybe the same or similar to the centralized server device 820 as describedwith reference to FIG. 8. For instance, the distributed server devices910 may each comprise a processing component 930 and a communicationscomponent 940 which are the same or similar to the processing component830 and the communications component 840, respectively, as describedwith reference to FIG. 8. In another example, the distributed serverdevices 910 may communicate over a communications media 912 usingcommunications signals 914 via the communications components 940.

The distributed server devices 910 may comprise or employ one or moreserver programs that operate to perform various methodologies inaccordance with the described embodiments. In one embodiment, forexample, the distributed server devices 910 may each implement one ormore consumer-to-business servers 915. The consumer-to-business servers915 may collectively implement the consumer-to-business service 110 as adistributed computing entity. The consumer-to-business servers 915 maycommunicate with a plurality of client devices 920, such as may comprisethe client device 120, client device 320, sender client device 520,recipient client device 590, client devices 810, or any other clientdevice.

FIG. 10 illustrates an embodiment of an exemplary computing architecture1000 suitable for implementing various embodiments as previouslydescribed. In one embodiment, the computing architecture 1000 maycomprise or be implemented as part of an electronic device. Examples ofan electronic device may include those described with reference to FIG.8, among others. The embodiments are not limited in this context.

As used in this application, the terms “system” and “component” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution, examples of which are provided by the exemplary computingarchitecture 1000. For example, a component can be, but is not limitedto being, a process running on a processor, a processor, a hard diskdrive, multiple storage drives (of optical and/or magnetic storagemedium), an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a server and the server can be a component. One or more componentscan reside within a process and/or thread of execution, and a componentcan be localized on one computer and/or distributed between two or morecomputers. Further, components may be communicatively coupled to eachother by various types of communications media to coordinate operations.The coordination may involve the uni-directional or bi-directionalexchange of information. For instance, the components may communicateinformation in the form of signals communicated over the communicationsmedia. The information can be implemented as signals allocated tovarious signal lines. In such allocations, each message is a signal.Further embodiments, however, may alternatively employ data messages.Such data messages may be sent across various connections. Exemplaryconnections include parallel interfaces, serial interfaces, and businterfaces.

The computing architecture 1000 includes various common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components, power supplies, and so forth.The embodiments, however, are not limited to implementation by thecomputing architecture 1000.

As shown in FIG. 10, the computing architecture 1000 comprises aprocessing unit 1004, a system memory 1006 and a system bus 1008. Theprocessing unit 1004 can be any of various commercially availableprocessors, including without limitation an AMD® Athlon®, Duron® andOpteron® processors; ARM® application, embedded and secure processors;IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony®Cell processors; Intel® Celeron®, Core (2) Duo®, Itanium®, Pentium®,Xeon®, and XScale® processors; and similar processors. Dualmicroprocessors, multi-core processors, and other multi-processorarchitectures may also be employed as the processing unit 1004.

The system bus 1008 provides an interface for system componentsincluding, but not limited to, the system memory 1006 to the processingunit 1004. The system bus 1008 can be any of several types of busstructure that may further interconnect to a memory bus (with or withouta memory controller), a peripheral bus, and a local bus using any of avariety of commercially available bus architectures. Interface adaptersmay connect to the system bus 1008 via a slot architecture. Example slotarchitectures may include without limitation Accelerated Graphics Port(AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA),Micro Channel Architecture (MCA), NuBus, Peripheral ComponentInterconnect (Extended) (PCI(X)), PCI Express, Personal Computer MemoryCard International Association (PCMCIA), and the like.

The computing architecture 1000 may comprise or implement variousarticles of manufacture. An article of manufacture may comprise acomputer-readable storage medium to store logic. Examples of acomputer-readable storage medium may include any tangible media capableof storing electronic data, including volatile memory or non-volatilememory, removable or non-removable memory, erasable or non-erasablememory, writeable or re-writeable memory, and so forth. Examples oflogic may include executable computer program instructions implementedusing any suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code,object-oriented code, visual code, and the like. Embodiments may also beat least partly implemented as instructions contained in or on anon-transitory computer-readable medium, which may be read and executedby one or more processors to enable performance of the operationsdescribed herein.

The system memory 1006 may include various types of computer-readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information. In the illustratedembodiment shown in FIG. 10, the system memory 1006 can includenon-volatile memory 1010 and/or volatile memory 1012. A basicinput/output system (BIOS) can be stored in the non-volatile memory1010.

The computer 1002 may include various types of computer-readable storagemedia in the form of one or more lower speed memory units, including aninternal (or external) hard disk drive (HDD) 1014, a magnetic floppydisk drive (FDD) 1016 to read from or write to a removable magnetic disk1018, and an optical disk drive 1020 to read from or write to aremovable optical disk 1022 (e.g., a CD-ROM or DVD). The HDD 1014, FDD1016 and optical disk drive 1020 can be connected to the system bus 1008by a HDD interface 1024, an FDD interface 1026 and an optical driveinterface 1028, respectively. The HDD interface 1024 for external driveimplementations can include at least one or both of Universal Serial Bus(USB) and IEEE 1394 interface technologies.

The drives and associated computer-readable media provide volatileand/or nonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For example, a number of program modules canbe stored in the drives and memory units 1010, 1012, including anoperating system 1030, one or more application programs 1032, otherprogram modules 1034, and program data 1036. In one embodiment, the oneor more application programs 1032, other program modules 1034, andprogram data 1036 can include, for example, the various applicationsand/or components of the consumer-to-business messaging system 100.

A user can enter commands and information into the computer 1002 throughone or more wire/wireless input devices, for example, a keyboard 1038and a pointing device, such as a mouse 1040. Other input devices mayinclude microphones, infra-red (IR) remote controls, radio-frequency(RF) remote controls, game pads, stylus pens, card readers, dongles,finger print readers, gloves, graphics tablets, joysticks, keyboards,retina readers, touch screens (e.g., capacitive, resistive, etc.),trackballs, trackpads, sensors, styluses, and the like. These and otherinput devices are often connected to the processing unit 1004 through aninput device interface 1042 that is coupled to the system bus 1008, butcan be connected by other interfaces such as a parallel port, IEEE 1394serial port, a game port, a USB port, an IR interface, and so forth.

A monitor 1044 or other type of display device is also connected to thesystem bus 1008 via an interface, such as a video adaptor 1046. Themonitor 1044 may be internal or external to the computer 1002. Inaddition to the monitor 1044, a computer typically includes otherperipheral output devices, such as speakers, printers, and so forth.

The computer 1002 may operate in a networked environment using logicalconnections via wire and/or wireless communications to one or moreremote computers, such as a remote computer 1048. The remote computer1048 can be a workstation, a server computer, a router, a personalcomputer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1002, although, for purposes of brevity, only a memory/storage device1050 is illustrated. The logical connections depicted includewire/wireless connectivity to a local area network (LAN) 1052 and/orlarger networks, for example, a wide area network (WAN) 1054. Such LANand WAN networking environments are commonplace in offices andcompanies, and facilitate enterprise-wide computer networks, such asintranets, all of which may connect to a global communications network,for example, the Internet.

When used in a LAN networking environment, the computer 1002 isconnected to the LAN 1052 through a wire and/or wireless communicationnetwork interface or adaptor 1056. The adaptor 1056 can facilitate wireand/or wireless communications to the LAN 1052, which may also include awireless access point disposed thereon for communicating with thewireless functionality of the adaptor 1056.

When used in a WAN networking environment, the computer 1002 can includea modem 1058, or is connected to a communications server on the WAN1054, or has other means for establishing communications over the WAN1054, such as by way of the Internet. The modem 1058, which can beinternal or external and a wire and/or wireless device, connects to thesystem bus 1008 via the input device interface 1042. In a networkedenvironment, program modules depicted relative to the computer 1002, orportions thereof, can be stored in the remote memory/storage device1050. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer 1002 is operable to communicate with wire and wirelessdevices or entities using the IEEE 802 family of standards, such aswireless devices operatively disposed in wireless communication (e.g.,IEEE 802.10 over-the-air modulation techniques). This includes at leastWi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wirelesstechnologies, among others. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.10x (a, b, g, n, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions).

FIG. 11 illustrates a block diagram of an exemplary communicationsarchitecture 1100 suitable for implementing various embodiments aspreviously described. The communications architecture 1100 includesvarious common communications elements, such as a transmitter, receiver,transceiver, radio, network interface, baseband processor, antenna,amplifiers, filters, power supplies, and so forth. The embodiments,however, are not limited to implementation by the communicationsarchitecture 1100.

As shown in FIG. 11, the communications architecture 1100 comprisesincludes one or more clients 1102 and servers 1104. The clients 1102 maycorrespond to messaging clients, as may be executed by any of the clientdevice 120, client device 320, sender client device 520, recipientclient device 590, client devices 810, client devices 920, or any otherclient device. The servers 1104 may implement the consumer-to-businessservice 110, as may be distributed across one or more server devices.The clients 1102 and the servers 1104 are operatively connected to oneor more respective client data stores 1108 and server data stores 1110that can be employed to store information local to the respectiveclients 1102 and servers 1104, such as cookies and/or associatedcontextual information.

The clients 1102 and the servers 1104 may communicate informationbetween each other using a communication framework 1106. Thecommunications framework 1106 may implement any well-knowncommunications techniques and protocols. The communications framework1106 may be implemented as a packet-switched network (e.g., publicnetworks such as the Internet, private networks such as an enterpriseintranet, and so forth), a circuit-switched network (e.g., the publicswitched telephone network), or a combination of a packet-switchednetwork and a circuit-switched network (with suitable gateways andtranslators).

The communications framework 1106 may implement various networkinterfaces arranged to accept, communicate, and connect to acommunications network. A network interface may be regarded as aspecialized form of an input output interface. Network interfaces mayemploy connection protocols including without limitation direct connect,Ethernet (e.g., thick, thin, twisted pair 10/100/1000 Base T, and thelike), token ring, wireless network interfaces, cellular networkinterfaces, IEEE 802.11a-x network interfaces, IEEE 802.16 networkinterfaces, IEEE 802.20 network interfaces, and the like. Further,multiple network interfaces may be used to engage with variouscommunications network types. For example, multiple network interfacesmay be employed to allow for the communication over broadcast,multicast, and unicast networks. Should processing requirements dictatea greater amount speed and capacity, distributed network controllerarchitectures may similarly be employed to pool, load balance, andotherwise increase the communicative bandwidth required by clients 1102and the servers 1104. A communications network may be any one and thecombination of wired and/or wireless networks including withoutlimitation a direct interconnection, a secured custom connection, aprivate network (e.g., an enterprise intranet), a public network (e.g.,the Internet), a Personal Area Network (PAN), a Local Area Network(LAN), a Metropolitan Area Network (MAN), an Operating Missions as Nodeson the Internet (OMNI), a Wide Area Network (WAN), a wireless network, acellular network, and other communications networks.

FIG. 12 illustrates an embodiment of a device 1200 for use in amulticarrier OFDM system, such as the consumer-to-business messagingsystem 100. Device 1200 may implement, for example, software components1260 as described with reference to consumer-to-business messagingsystem 100 and/or a logic circuit 1235. The logic circuit 1235 mayinclude physical circuits to perform operations described for theconsumer-to-business messaging system 100. As shown in FIG. 12, device1200 may include a radio interface 1210, baseband circuitry 1220, andcomputing platform 1230, although embodiments are not limited to thisconfiguration.

The device 1200 may implement some or all of the structure and/oroperations for the consumer-to-business messaging system 100 and/orlogic circuit 1235 in a single computing entity, such as entirely withina single device. Alternatively, the device 1200 may distribute portionsof the structure and/or operations for the consumer-to-businessmessaging system 100 and/or logic circuit 1235 across multiple computingentities using a distributed system architecture, such as aclient-server architecture, a 3-tier architecture, an N-tierarchitecture, a tightly-coupled or clustered architecture, apeer-to-peer architecture, a master-slave architecture, a shareddatabase architecture, and other types of distributed systems. Theembodiments are not limited in this context.

In one embodiment, radio interface 1210 may include a component orcombination of components adapted for transmitting and/or receivingsingle carrier or multi-carrier modulated signals (e.g., includingcomplementary code keying (CCK) and/or orthogonal frequency divisionmultiplexing (OFDM) symbols) although the embodiments are not limited toany specific over-the-air interface or modulation scheme. Radiointerface 1210 may include, for example, a receiver 1212, a transmitter1216 and/or a frequency synthesizer 1214. Radio interface 1210 mayinclude bias controls, a crystal oscillator and/or one or more antennas1218. In another embodiment, radio interface 1210 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

Baseband circuitry 1220 may communicate with radio interface 1210 toprocess receive and/or transmit signals and may include, for example, ananalog-to-digital converter 1222 for down converting received signals, adigital-to-analog converter 1224 for up converting signals fortransmission. Further, baseband circuitry 1220 may include a baseband orphysical layer (PHY) processing circuit 1256 for PHY link layerprocessing of respective receive/transmit signals. Baseband circuitry1220 may include, for example, a processing circuit 1228 for mediumaccess control (MAC)/data link layer processing. Baseband circuitry 1220may include a memory controller 1232 for communicating with processingcircuit 1228 and/or a computing platform 1230, for example, via one ormore interfaces 1234.

In some embodiments, PHY processing circuit 1226 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames, such as radio frames. Alternatively or inaddition, MAC processing circuit 1228 may share processing for certainof these functions or perform these processes independent of PHYprocessing circuit 1226. In some embodiments, MAC and PHY processing maybe integrated into a single circuit.

The computing platform 1230 may provide computing functionality for thedevice 1200. As shown, the computing platform 1230 may include aprocessing component 1240. In addition to, or alternatively of, thebaseband circuitry 1220, the device 1200 may execute processingoperations or logic for the consumer-to-business messaging system 100and logic circuit 1235 using the processing component 1240. Theprocessing component 1240 (and/or PHY 1226 and/or MAC 1228) may comprisevarious hardware elements, software elements, or a combination of both.Examples of hardware elements may include devices, logic devices,components, processors, microprocessors, circuits, processor circuits,circuit elements (e.g., transistors, resistors, capacitors, inductors,and so forth), integrated circuits, application specific integratedcircuits (ASIC), programmable logic devices (PLD), digital signalprocessors (DSP), field programmable gate array (FPGA), memory units,logic gates, registers, semiconductor device, chips, microchips, chipsets, and so forth. Examples of software elements may include softwarecomponents, programs, applications, computer programs, applicationprograms, system programs, software development programs, machineprograms, operating system software, middleware, firmware, softwaremodules, routines, subroutines, functions, methods, procedures, softwareinterfaces, application program interfaces (API), instruction sets,computing code, computer code, code segments, computer code segments,words, values, symbols, or any combination thereof. Determining whetheran embodiment is implemented using hardware elements and/or softwareelements may vary in accordance with any number of factors, such asdesired computational rate, power levels, heat tolerances, processingcycle budget, input data rates, output data rates, memory resources,data bus speeds and other design or performance constraints, as desiredfor a given implementation.

The computing platform 1230 may further include other platformcomponents 1250. Other platform components 1250 include common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components (e.g., digital displays), powersupplies, and so forth. Examples of memory units may include withoutlimitation various types of computer readable and machine readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

Device 1200 may be, for example, an ultra-mobile device, a mobiledevice, a fixed device, a machine-to-machine (M2M) device, a personaldigital assistant (PDA), a mobile computing device, a smart phone, atelephone, a digital telephone, a cellular telephone, user equipment,eBook readers, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, television, digitaltelevision, set top box, wireless access point, base station, node B,evolved node B (eNB), subscriber station, mobile subscriber center,radio network controller, router, hub, gateway, bridge, switch, machine,or combination thereof. Accordingly, functions and/or specificconfigurations of device 1200 described herein, may be included oromitted in various embodiments of device 1200, as suitably desired. Insome embodiments, device 1200 may be configured to be compatible withprotocols and frequencies associated one or more of the 3GPP LTESpecifications and/or IEEE 1202.16 Standards for WMANs, and/or otherbroadband wireless networks, cited herein, although the embodiments arenot limited in this respect.

Embodiments of device 1200 may be implemented using single input singleoutput (SISO) architectures. However, certain implementations mayinclude multiple antennas (e.g., antennas 1218) for transmission and/orreception using adaptive antenna techniques for beamforming or spatialdivision multiple access (SDMA) and/or using MIMO communicationtechniques.

The components and features of device 1200 may be implemented using anycombination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of device 1200 may be implemented using microcontrollers,programmable logic arrays and/or microprocessors or any combination ofthe foregoing where suitably appropriate. It is noted that hardware,firmware and/or software elements may be collectively or individuallyreferred to herein as “logic” or “circuit.”

It should be appreciated that the exemplary device 1200 shown in theblock diagram of FIG. 12 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would be necessarily bedivided, omitted, or included in embodiments.

A computer-implemented method may comprise monitoring a messaginginteraction, the messaging interaction exchanged via a messaging system,the messaging interaction involving at least one client device;detecting a user intent for the messaging interaction; determining amessaging bot options configuration for the client device based on theuser intent; and sending the messaging bot options configuration to theclient device.

A computer-implemented method may further comprise wherein detecting theuser intent for the messaging interaction comprises: submitting at leasta portion of the messaging interaction to a natural-language machinelearning component; and receiving the user intent from thenatural-language machine learning component in response to submitting atleast the portion of the messaging interaction to the natural-languagemachine learning component.

A computer-implemented method may further comprise the messaginginteraction comprising a plurality of exchanged messages, the pluralityof exchanged messages comprising a most-recent message of the messageinteraction, further comprising: sending a message package to the clientdevice, the message package associated with the most-recent message, themessage package comprising the messaging bot options configuration.

A computer-implemented method may further comprise the message packageupdating the client device with the most-recent message, the most-recentmessage received from a different client device.

A computer-implemented method may further comprise the message packageacknowledging receipt of the most-recent message from the client device.

A computer-implemented method may further comprise the messaging botoptions configuration comprising a messaging bot menu associated with amessaging bot, wherein the messaging bot menu is customized based on theuser intent.

A computer-implemented method may further comprise wherein the messagingbot menu comprises a plurality of user-customizable options, whereincustomizing the messaging bot menu based on the user intent comprisespre-filling one or more of the user-customizable options based on theuser intent.

A computer-implemented method may further comprise wherein customizingthe messaging bot menu based on the user intent comprises selecting amenu section of the menu for display on the client device based on theuser intent.

A computer-implemented method may further comprise the messaging botoptions configuration comprising a plurality of messaging bot invocationcontrols, wherein each of the messaging bot invocation controls isassociated with a different messaging bot, wherein the plurality ofmessaging bot invocation controls are selected based on the user intent.

A computer-implemented method may further comprise wherein the pluralityof messaging bot invocation controls are additionally selected based ona user context.

A computer-implemented method may further comprise the user contextcomprising one or more of a user location and a local user time.

A computer-implemented method may further comprise wherein the pluralityof messaging bot invocation controls are additionally selected based ona user profile, the user profile comprising user service preferenceinformation.

A computer-implemented method may further comprise receiving a usermessaging bot selection of a selected messaging bot invocation controlof the plurality of messaging bot invocation controls from the clientdevice, the selected messaging bot invocation control associated with aselected messaging bot; and sending a messaging bot interface to theclient device in response to receiving the invocation of the selectedmessaging bot invocation control.

A computer-implemented method may further comprise sending a messagingbot invocation message to a bot server associated with the selectedmessaging bot, the messaging bot invocation message comprising the userintent; and receiving a messaging bot interface specification from thebot server in response to the messaging bot invocation message, themessaging bot interface based on the messaging bot interfacespecification.

A computer-implemented method may further comprise the messaging botinterface comprising a plurality of user-customizable options, furthercomprising: receiving one or more user option configurations for theplurality of user-customizable options; receiving a second usermessaging bot selection of a second messaging bot invocation control ofthe plurality of messaging bot invocation controls from the clientdevice, the second selected messaging bot invocation control associatedwith a second selected messaging bot distinct from the selectedmessaging bot; sending a second messaging bot interface to the clientdevice in response to receiving the invocation of the selected messagingbot invocation control, the second messaging bot interface associatedwith the second selected messaging bot; and configuring the secondmessaging bot interface based on the one or more user optionconfigurations, wherein configuring the second messaging bot interfacebased on the one or more user option configurations transitions the oneor more user option configurations to the second messaging botinterface.

An apparatus may comprise a processor circuit on a device; a messagequeue monitoring component operative on the processor circuit to monitora messaging interaction, the messaging interaction exchanged via amessaging system, the messaging interaction involving at least oneclient device; an interaction processing component operative todetermine a user intent for the messaging interaction; and a botmanagement component operative to determine a messaging bot optionsconfiguration for the client device based on the user intent; and sendthe messaging bot options configuration to the client device. Theapparatus may be operative to implement any of the computer-implementedmethods described herein.

At least one computer-readable storage medium may comprise instructionsthat, when executed, cause a system to perform any of thecomputer-implemented methods described herein.

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Further, some embodiments may be described using the expression“coupled” and “connected” along with their derivatives. These terms arenot necessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

With general reference to notations and nomenclature used herein, thedetailed descriptions herein may be presented in terms of programprocedures executed on a computer or network of computers. Theseprocedural descriptions and representations are used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art.

A procedure is here, and generally, conceived to be a self-consistentsequence of operations leading to a desired result. These operations arethose requiring physical manipulations of physical quantities. Usually,though not necessarily, these quantities take the form of electrical,magnetic or optical signals capable of being stored, transferred,combined, compared, and otherwise manipulated. It proves convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, values, elements, symbols, characters, terms, numbers,or the like. It should be noted, however, that all of these and similarterms are to be associated with the appropriate physical quantities andare merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein which form part of one or more embodiments.Rather, the operations are machine operations. Useful machines forperforming operations of various embodiments include general purposedigital computers or similar devices.

Various embodiments also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for therequired purpose or it may comprise a general purpose computer asselectively activated or reconfigured by a computer program stored inthe computer. The procedures presented herein are not inherently relatedto a particular computer or other apparatus. Various general purposemachines may be used with programs written in accordance with theteachings herein, or it may prove convenient to construct morespecialized apparatus to perform the required method steps. The requiredstructure for a variety of these machines will appear from thedescription given.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thusthe following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment. In the appended claims, the terms “including” and “in which”are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

What is claimed is:
 1. A computer-implemented method, comprising:monitoring a messaging interaction, the messaging interaction exchangedvia a messaging system, the messaging interaction involving at least oneclient device; detecting a user intent for the messaging interaction;determining a messaging bot options configuration for the client devicebased on the user intent; and sending the messaging bot optionsconfiguration to the client device.
 2. The method of claim 1, themessaging bot options configuration comprising a messaging bot menuassociated with a messaging bot, wherein the messaging bot menu iscustomized based on the user intent.
 3. The method of claim 2, whereinthe messaging bot menu comprises a plurality of user-customizableoptions, wherein customizing the messaging bot menu based on the userintent comprises pre-filling one or more of the user-customizableoptions based on the user intent.
 4. The method of claim 2, whereincustomizing the messaging bot menu based on the user intent comprisesselecting a menu section of the menu for display on the client devicebased on the user intent.
 5. The method of claim 1, the messaging botoptions configuration comprising a plurality of messaging bot invocationcontrols, wherein each of the messaging bot invocation controls isassociated with a different messaging bot, wherein the plurality ofmessaging bot invocation controls are selected based on the user intent.6. The method of claim 5, further comprising: receiving a user messagingbot selection of a selected messaging bot invocation control of theplurality of messaging bot invocation controls from the client device,the selected messaging bot invocation control associated with a selectedmessaging bot; and sending a messaging bot interface to the clientdevice in response to receiving the invocation of the selected messagingbot invocation control.
 7. The method of claim 6, further comprising:sending a messaging bot invocation message to a bot server associatedwith the selected messaging bot, the messaging bot invocation messagecomprising the user intent; and receiving a messaging bot interfacespecification from the bot server in response to the messaging botinvocation message, the messaging bot interface based on the messagingbot interface specification.
 8. The method of claim 6, the messaging botinterface comprising a plurality of user-customizable options, furthercomprising: receiving one or more user option configurations for theplurality of user-customizable options; receiving a second usermessaging bot selection of a second messaging bot invocation control ofthe plurality of messaging bot invocation controls from the clientdevice, the second selected messaging bot invocation control associatedwith a second selected messaging bot distinct from the selectedmessaging bot; sending a second messaging bot interface to the clientdevice in response to receiving the invocation of the selected messagingbot invocation control, the second messaging bot interface associatedwith the second selected messaging bot; and configuring the secondmessaging bot interface based on the one or more user optionconfigurations, wherein configuring the second messaging bot interfacebased on the one or more user option configurations transitions the oneor more user option configurations to the second messaging botinterface.
 9. An apparatus, comprising: a processor circuit on a device;a message queue monitoring component operative on the processor circuitto monitor a messaging interaction, the messaging interaction exchangedvia a messaging system, the messaging interaction involving at least oneclient device; an interaction processing component operative todetermine a user intent for the messaging interaction; and a botmanagement component operative to determine a messaging bot optionsconfiguration for the client device based on the user intent; and sendthe messaging bot options configuration to the client device.
 10. Theapparatus of claim 9, the messaging bot options configuration comprisinga messaging bot menu associated with a messaging bot, wherein themessaging bot menu is customized based on the user intent, wherein themessaging bot menu comprises a plurality of user-customizable options,wherein customizing the messaging bot menu based on the user intentcomprises pre-filling one or more of the user-customizable options basedon the user intent.
 11. The apparatus of claim 9, the messaging botoptions configuration comprising a messaging bot menu associated with amessaging bot, wherein the messaging bot menu is customized based on theuser intent, wherein customizing the messaging bot menu based on theuser intent comprises selecting a menu section of the menu for displayon the client device based on the user intent.
 12. The apparatus ofclaim 9, the messaging bot options configuration comprising a pluralityof messaging bot invocation controls, wherein each of the messaging botinvocation controls is associated with a different messaging bot,wherein the plurality of messaging bot invocation controls are selectedbased on the user intent, further comprising: the bot managementcomponent operative to receive a user messaging bot selection of aselected messaging bot invocation control of the plurality of messagingbot invocation controls from the client device, the selected messagingbot invocation control associated with a selected messaging bot; andsend a messaging bot interface to the client device in response toreceiving the invocation of the selected messaging bot invocationcontrol.
 13. The apparatus of claim 12, further comprising: the botmanagement component operative to send a messaging bot invocationmessage to a bot server associated with the selected messaging bot, themessaging bot invocation message comprising the user intent; and receivea messaging bot interface specification from the bot server in responseto the messaging bot invocation message, the messaging bot interfacebased on the messaging bot interface specification.
 14. The apparatus ofclaim 12, the messaging bot interface comprising a plurality ofuser-customizable options, further comprising: the bot managementcomponent operative to receive one or more user option configurationsfor the plurality of user-customizable options; receive a second usermessaging bot selection of a second messaging bot invocation control ofthe plurality of messaging bot invocation controls from the clientdevice, the second selected messaging bot invocation control associatedwith a second selected messaging bot distinct from the selectedmessaging bot; send a second messaging bot interface to the clientdevice in response to receiving the invocation of the selected messagingbot invocation control, the second messaging bot interface associatedwith the second selected messaging bot; and configure the secondmessaging bot interface based on the one or more user optionconfigurations, wherein configuring the second messaging bot interfacebased on the one or more user option configurations transitions the oneor more user option configurations to the second messaging botinterface.
 15. At least one computer-readable storage medium comprisinginstructions that, when executed, cause a system to: monitor a messaginginteraction, the messaging interaction exchanged via a messaging system,the messaging interaction involving at least one client device; detect auser intent for the messaging interaction; determine a messaging botoptions configuration for the client device based on the user intent;and send the messaging bot options configuration to the client device.16. The computer-readable storage medium of claim 15, the messaging botoptions configuration comprising a messaging bot menu associated with amessaging bot, wherein the messaging bot menu is customized based on theuser intent, wherein the messaging bot menu comprises a plurality ofuser-customizable options, wherein customizing the messaging bot menubased on the user intent comprises pre-filling one or more of theuser-customizable options based on the user intent.
 17. Thecomputer-readable storage medium of claim 15, the messaging bot optionsconfiguration comprising a messaging bot menu associated with amessaging bot, wherein the messaging bot menu is customized based on theuser intent, wherein customizing the messaging bot menu based on theuser intent comprises selecting a menu section of the menu for displayon the client device based on the user intent.
 18. The computer-readablestorage medium of claim 15, the messaging bot options configurationcomprising a plurality of messaging bot invocation controls, whereineach of the messaging bot invocation controls is associated with adifferent messaging bot, wherein the plurality of messaging botinvocation controls are selected based on the user intent, comprisingfurther instructions that, when executed, cause a system to: receive auser messaging bot selection of a selected messaging bot invocationcontrol of the plurality of messaging bot invocation controls from theclient device, the selected messaging bot invocation control associatedwith a selected messaging bot; and send a messaging bot interface to theclient device in response to receiving the invocation of the selectedmessaging bot invocation control.
 19. The computer-readable storagemedium of claim 18, comprising further instructions that, when executed,cause a system to: send a messaging bot invocation message to a botserver associated with the selected messaging bot, the messaging botinvocation message comprising the user intent; and receive a messagingbot interface specification from the bot server in response to themessaging bot invocation message, the messaging bot interface based onthe messaging bot interface specification.
 20. The computer-readablestorage medium of claim 18, the messaging bot interface comprising aplurality of user-customizable options, comprising further instructionsthat, when executed, cause a system to: receive one or more user optionconfigurations for the plurality of user-customizable options; receive asecond user messaging bot selection of a second messaging bot invocationcontrol of the plurality of messaging bot invocation controls from theclient device, the second selected messaging bot invocation controlassociated with a second selected messaging bot distinct from theselected messaging bot; send a second messaging bot interface to theclient device in response to receiving the invocation of the selectedmessaging bot invocation control, the second messaging bot interfaceassociated with the second selected messaging bot; and configure thesecond messaging bot interface based on the one or more user optionconfigurations, wherein configuring the second messaging bot interfacebased on the one or more user option configurations transitions the oneor more user option configurations to the second messaging botinterface.